Generally, what we need from you are the steps necessary for us to duplicate the problem. However, we’d like you to try a test with CMaster inactive if the problem isn’t directly related to a CMaster feature (like, such and such a menu shows dimmed, and I don’t think it should.)
Steps:
1) Close the project, and reopen holding the option key down to open the project with CMaster inactive.
2) Try out the steps that caused the problem. Is it still there?
3) If still there, reopen. Now, if necessary, create a new file and add as few a number of lines as necessary to get it to do something wrong. If you can do this, email us this file, along with a description of what you think CMaster SHOULD be doing or showing.
4) If you have an issue of what CMaste shows in the Marker menu, be VERY specific as to what CMaster showed, and what you think it should show, and why.
If the problem is more complicated than can be shown in a simple text file, then move your prefs file to a safe folder, and copy the standard prefs file into the same folder as CMaster. Copy any resources to it that CMaster might need to dup your problem (like a color cursor, etc) but no more than necessary. Without changing the preferences, try and duplicate the problem. If it does not happen now, then change only those prefs that you must to make it happen. Record which ones changed, and report the problem along with the list of prefs that were changed.
Also, PLEASE include the CMaster version from the About Box, the THINK version from its About Box, and perhaps the machine type and MacOS version (if you’re having problems say with window colors on multiple monitor systems, then what the depth of each monitor is, etc.)
Don’t expect a response the same evening you send the mail to us. We first look at reports, then if the problem is not obvious, we have to set up a test, try to duplicate it, and if we can, then poke around our code. It may take a day or two. We’ll get back to you in a day or two. If your really want confirmation immediately that we got your mail, etc, then ask for it and we’ll try to get back to you within 24 hours.
We left MacsBug symbols on in this version, so if you get a crash please look at the A6 stack trace for function names. If the stack contains CCOD or PROC resources, that's CMaster (if you see CODE resources, that's THINK.) Send us the stack trace with your problem if at all possible.
